Applied Filters: (Reset All Filters)
Priority: alert ( Reset Filter)
Release: 9.2 ( Reset Filter)
| Date | Title | Type | ||
|---|---|---|---|---|
| 9/9/09 |
36587 - The Score Code Export node does not provide optimized score code The Score Code Export node outputs the un-optimized code that is generated with SAS® Enterprise Miner™ 6.1 instead of the optimized code. Select the Hot Fix tab in this note to access the hot fix for this ... http://support.sas.com/kb/36/587.html, 18KB |
Problem Note | ||
| 9/4/09 |
36626 - Incorrect dates are appended to the Sybase table when you use the APPEND procedure with the SASDATEFMT= and the BULKCOPY= options When you use SAS/ACCESS® Interface to Sybase with an APPEND procedure that contains SASDATEFMT= and the BULKCOPY=YES options, the date values are all changed to Jan 1, 1900. This problem occurs only when you use ... http://support.sas.com/kb/36/626.html, 19KB |
Problem Note | ||
| 7/14/09 |
35130 - SAS/ACCESS® Interface to Oracle is not supported on Linux for x64 when you run 32-bit SAS® software Oracle does not support 32-bit Oracle library on the Linux for x64 platform; therefore SAS/ACCESS® Interface to Oracle is not supported on Linux for x64 when you are run 32-bit SAS. With SAS® 9.2, the 64-bit version of ... http://support.sas.com/kb/35/130.html, 18KB |
Problem Note | ||
| 4/8/09 |
34687 - Incorrect results might occur if you use the PUT() function in a WHERE clause to convert a DB2 timestamp to a character value Incorrect results might occur if you use the PUT() function in a WHERE clause to convert a DB2 timestamp to a character value so it can be compared to a constant in the WHERE clause. Even if matches exist, they will not ... http://support.sas.com/kb/34/687.html, 19KB |
Problem Note | ||
| 8/4/06 |
18020 - SAS® OLAP Server may error when empty data is passed to certain SAS® functions SAS function calls that contain empty data may cause an exception when returned by the SAS OLAP Server. This typically will be seen when creating a calculated measure that utilizes one of the available functions, such ... http://support.sas.com/kb/18/020.html, 19KB |
Problem Note | ||
| 10/21/05 |
15241 - Oracle minimum requirements change with Service Pack 3 on z/OS Starting with SAS® 9.1 TS1M3 Service Pack 3, the minimum required Oracle client compatible with SAS/Access Interface to Oracle on z/OS will be Oracle 9i. Beginning with SAS 9.1.3 Service Pack 3, the Oracle 8i ... http://support.sas.com/kb/15/241.html, 18KB |
Usage Note | ||
| 3/6/03 |
9562 - Publishing package is replaced when publishing from the SAS/PUBLISH frame to a WebDAV compliant server Using SAS/Integration Technologies Publish Framework to publish, may result in the contents of the entire package being replaced. This problem will occur if the existing package is published to a WebDAV compliant ... http://support.sas.com/kb/9/562.html, 19KB |
Problem Note | ||
| 8/23/01 |
5682 - ERROR: Teradata connection: MOSI: ER_LINKDOWN(130):DBC Connection broken or connect failed The SAS/ACCESS Interface to Teradata product is installed when you unload the SAS media; however, you must run the correct SAS image or you will receive execution messages similar to those below: ERROR: Teradata ... http://support.sas.com/kb/5/682.html, 17KB |
Usage Note | ||
| 6/25/01 |
4198 - When using the OLE DB Jet 4.0 provider shipped with the MDAC, Version 2.1.2 GA and Version 2.5 release, the OLEDB libname engine will improperly delete records. When using the OLE DB Jet 4.0 provider shipped with the MDAC, Version 2.1.2 GA and Version 2.5 release, the OLEDB libname engine will incorrectly delete only two records. It will delete only two records although there ... http://support.sas.com/kb/4/198.html, 18KB |
Usage Note | ||
| 6/25/01 |
4197 - When using SAS/ACCESS Interface to OLE/DB to update Microsoft SQL Server, V7 data through WHERE clause processing might be unreliable When you use SAS/ACCESS Interface to OLE/DB to update Microsoft SQL Server, Version 7 data through WHERE clause processing might result in unreliable updates. The problem only occurs when using Microsoft SQL Server with ... http://support.sas.com/kb/4/197.html, 19KB |
Usage Note | ||
